System and method for determining power supply unit configurations in an information handling system

ABSTRACT

A method determines power supply unit configurations in an information handling system. The method includes determining, via a controller, a first amount of power required to operate functional components of the IHS. A history table is retrieved containing a plurality of power supply unit (PSU) configurations and PSU data. The method further includes determining if the history table contains a first PSU configuration corresponding to the first amount of power. In response to determining that the history table contains the first PSU configuration corresponding to the first amount of power, the PSUs identified as active mode PSUs in the first PSU configuration are triggered to be in an active mode and operating at the corresponding percentage load and the PSUs identified as sleep mode PSUs in the first PSU configuration are triggered to be in a sleep mode.

BACKGROUND

1. Technical Field

The present disclosure generally relates to information handling systemsand in particular to a system and method for determining power supplyunit configurations in an information handling system.

2. Description of the Related Art

As the value and use of information continue to increase, individualsand businesses seek additional ways to process and store information.One option available to users is information handling systems. Aninformation handling system generally processes, compiles, stores,and/or communicates information or data for business, personal, or otherpurposes, thereby allowing users to take advantage of the value of theinformation. Because technology and information handling needs andrequirements vary between different users or applications, informationhandling systems may also vary regarding what information is handled,how the information is handled, how much information is processed,stored, or communicated, and how quickly and efficiently the informationmay be processed, stored, or communicated. The variations in informationhandling systems allow for information handling systems to be general orconfigured for a specific user or specific use such as financialtransaction processing, airline reservations, enterprise data storage,or global communications. In addition, information handling systems mayinclude a variety of hardware and software components that may beconfigured to process, store, and communicate information and mayinclude one or more computer systems, data storage systems, andnetworking systems.

An information handling system may include a number of redundantalternating current to direct current (AC-DC) or direct current todirect current (DC-DC) power supplies that provide regulated voltages todifferent loads. The load current may vary across a broad range fromrelatively high peak currents to very low stable currents. The AC-DC andDC-DC power supplies used in servers typically should be designed for alarge range of server configurations and generally need to be designedto handle the full load of the server safely. The power supplies alsoneed to be optimized for efficiency, size, and cost.

In many applications, reliability or availability of the informationhandling system is an important factor. Redundant power supplies providean equivalent power back up when one or more power supplies discontinueoperation. Multiple power supplies provide redundancy by being coupledto a common output bus. Wherever more than one power supply exists, thepower supplies can be designated to be in various states or modes suchas active, sleep, hot-spare or cold spare. Typically the selection ofwhich power supplies are active and which power supplies are in a sleepmode are pre-determined by a user during configuration of the system. Ifone power supply fails, one of the redundant power supplies can bebrought online to replace the failed power supply.

BRIEF SUMMARY

Disclosed are a method, a power supply system, and an informationhandling system (IHS) for determining power supply unit (PSU)configurations in an IHS.

As one aspect of the disclosure, a history table is generated bytriggering the PSUs to be in a plurality of combinations of active andsleep modes and triggering the PSUs to transmit PSU parametersassociated with operation of the PSU at each of the plurality ofpercentage loads and for each of the plurality of combinations. The PSUparameters for the plurality of percentage loads for each of theplurality of combinations are stored as the plurality of PSUconfigurations.

According to one embodiment, the method comprises determining, via acontroller, a first amount of power required to operate functionalcomponents of the IHS. The first amount of power correlates to a presentpercentage load on a plurality of PSUs utilized to power the IHS. Thehistory table containing a plurality of power supply unit (PSU)configurations and PSU data is retrieved. The PSU configurations includecombinations of active mode and sleep mode PSUs for each of a pluralityof percentage loads. The method further includes determining if thehistory table contains a first PSU configuration corresponding to thefirst amount of power required to operate functional components of theIHS. In response to determining that the history table contains thefirst PSU configuration, the PSUs identified as active mode PSUs in thefirst PSU configuration are triggered to be in an active mode and tocollectively operate at the corresponding percentage load, and the PSUsidentified as sleep mode PSUs in the first PSU configuration areconfigured to be in a sleep mode.

According to another embodiment, a power supply system comprises aplurality of PSUs supplying power to an IHS. A controller iscommunicatively coupled to the PSUs. The controller has firmwareexecuting thereon to determine at least one PSU configuration to applyto the IHS. The firmware configures the controller to determine a firstamount of power required to operate functional components of the IHS.The first amount of power correlates to a present percentage load on theplurality of PSUs utilized to power the IHS. The history tablecontaining a plurality of PSU configurations and PSU data is retrieved.The controller determines if the history table contains a first PSUconfiguration corresponding to the first amount of power required tooperate functional components of the IHS. In response to determiningthat the history table contains the first PSU configuration, thecontroller triggers the PSUs identified as active mode PSUs in the firstPSU configuration to be in an active mode and collectively operating atthe corresponding percentage load. The PSUs identified as sleep modePSUs in the first PSU configuration are triggered to be in a sleep mode.

Also disclosed is an IHS that comprises a processor and a plurality ofPSUs that are configurable in one of multiple different powerconfigurations to supply power to the IHS. A controller iscommunicatively coupled to the plurality of PSUs. The controller hasfirmware executing thereon to determine at least one PSU configuration.The firmware configures the controller to determine a first amount ofpower required to operate functional components of the IHS. The firstamount of power correlates to a present percentage load on the pluralityof PSUs utilized to power the IHS. The history table containing aplurality of PSU configurations and PSU data is retrieved. Thecontroller determines if the history table contains a first PSUconfiguration corresponding to the first amount of power required tooperate functional components of the IHS. In response to determiningthat the history table contains the first PSU configuration, the PSUsidentified as active mode PSUs in the first PSU configuration aretriggered by the controller to be in an active mode and collectivelyoperating at the corresponding percentage load. The PSUs identified assleep mode PSUs in the first PSU configuration are triggered to be in asleep mode.

The above summary contains simplifications, generalizations andomissions of detail and is not intended as a comprehensive descriptionof the claimed subject matter but, rather, is intended to provide abrief overview of some of the functionality associated therewith. Othersystems, methods, functionality, features and advantages of the claimedsubject matter will be or will become apparent to one with skill in theart upon examination of the following figures and detailed writtendescription.

BRIEF DESCRIPTION OF THE DRAWINGS

The description of the illustrative embodiments can be read inconjunction with the accompanying figures. It will be appreciated thatfor simplicity and clarity of illustration, elements illustrated in thefigures have not necessarily been drawn to scale. For example, thedimensions of some of the elements are exaggerated relative to otherelements. Embodiments incorporating teachings of the present disclosureare shown and described with respect to the figures presented herein, inwhich:

FIG. 1 illustrates an example information handling system within whichvarious aspects of the disclosure can be implemented, according to oneor more embodiments;

FIG. 2A is a block diagram illustrating a physical layout of componentsand temperature zones within the example information handling system, inaccordance with one embodiment;

FIG. 2B is a block diagram illustrating a physical layout of componentsand temperature zones within the example information handling system, inaccordance with another embodiment;

FIG. 3 is a block diagram of an example PSU, in accordance with oneembodiment;

FIG. 4A is a block diagram illustrating example contents of the memoryof the PSU control system, in accordance with one embodiment;

FIGS. 4B and 4C are block diagrams illustrating an example historytable, in accordance with one embodiment;

FIG. 5 is a flow chart illustrating one example of a method fordetermining active and sleep mode PSUs in an information handlingsystem, according to one or more embodiments;

FIGS. 6A and 6B is a flow chart illustrating an example of a method forpre-populating a history table during a POST operation of an informationhandling system, according to one or more embodiments; and

FIGS. 7A and 7B is a flow chart illustrating an additional example of amethod for determining active and sleep mode PSUs in an informationhandling system, according to one or more embodiments.

DETAILED DESCRIPTION

The illustrative embodiments provide a method, a power supply system,and an information handling system (IHS) for determining PSUconfigurations in an IHS.

In the following detailed description of exemplary embodiments of thedisclosure, specific exemplary embodiments in which the disclosure maybe practiced are described in sufficient detail to enable those skilledin the art to practice the disclosed embodiments. For example, specificdetails such as specific method orders, structures, elements, andconnections have been presented herein. However, it is to be understoodthat the specific details presented need not be utilized to practiceembodiments of the present disclosure. It is also to be understood thatother embodiments may be utilized and that logical, architectural,programmatic, mechanical, electrical and other changes may be madewithout departing from general scope of the disclosure. The followingdetailed description is, therefore, not to be taken in a limiting sense,and the scope of the present disclosure is defined by the appendedclaims and equivalents thereof.

References within the specification to “one embodiment,” “anembodiment,” “embodiments”, or “one or more embodiments” are intended toindicate that a particular feature, structure, or characteristicdescribed in connection with the embodiment is included in at least oneembodiment of the present disclosure. The appearance of such phrases invarious places within the specification are not necessarily allreferring to the same embodiment, nor are separate or alternativeembodiments mutually exclusive of other embodiments. Further, variousfeatures are described which may be exhibited by some embodiments andnot by others. Similarly, various requirements are described which maybe requirements for some embodiments but not other embodiments.

It is understood that the use of specific component, device and/orparameter names and/or corresponding acronyms thereof, such as those ofthe executing utility, logic, and/or firmware described herein, are forexample only and not meant to imply any limitations on the describedembodiments. The embodiments may thus be described with differentnomenclature and/or terminology utilized to describe the components,devices, parameters, methods and/or functions herein, withoutlimitation. References to any specific protocol or proprietary name indescribing one or more elements, features or concepts of the embodimentsare provided solely as examples of one implementation, and suchreferences do not limit the extension of the claimed embodiments toembodiments in which different element, feature, protocol, or conceptnames are utilized. Thus, each term utilized herein is to be given itsbroadest interpretation given the context in which that term isutilized.

FIG. 1 illustrates a block diagram representation of an exampleinformation handling system (IHS) 100, within which one or more of thedescribed features of the various embodiments of the disclosure can beimplemented. For purposes of this disclosure, an information handlingsystem, such as IHS 100, may include any instrumentality or aggregate ofinstrumentalities operable to compute, classify, process, transmit,receive, retrieve, originate, switch, store, display, manifest, detect,record, reproduce, handle, or utilize any form of information,intelligence, or data for business, scientific, control, or otherpurposes. For example, an information handling system may be a handhelddevice, personal computer, a server, a network storage device, or anyother suitable device and may vary in size, shape, performance,functionality, and price. The information handling system may includerandom access memory (RAM), one or more processing resources such as acentral processing unit (CPU) or hardware or software control logic,ROM, and/or other types of nonvolatile memory. Additional components ofthe information handling system may include one or more disk drives, oneor more network ports for communicating with external devices as well asvarious input and output (I/O) devices, such as a keyboard, a mouse, anda video display. The information handling system may also include one ormore buses operable to transmit communications between the varioushardware components.

Referring specifically to FIG. 1, example IHS 100 includes one or moreprocessor(s) 105 coupled to system memory 110 via system interconnect115. System interconnect 115 can be interchangeably referred to as asystem bus, in one or more embodiments. Also coupled to systeminterconnect 115 is storage 120 within which can be stored one or moresoftware and/or firmware modules and/or data (not specifically shown).In one embodiment, storage 120 can be hard drive or a solid state drive.The one or more software and/or firmware modules within storage 120 canbe loaded into system memory 110 during operation of IHS 100. As shown,system memory 110 can include therein a plurality of software and/orfirmware modules including firmware (F/W) 112, basic input/output system(BIOS) 114, operating system (O/S) 116, and application(s) 118.

In one or more embodiments, BIOS 114 comprises additional functionalityassociated with unified extensible firmware interface (UEFI), and isthus illustrated as and can be more completely referred to as BIOS/UEFIin these embodiments. The various software and/or firmware modules havevarying functionality when their corresponding program code is executedby processor(s) 105 or other processing devices within IHS 100.

IHS 100 further includes one or more input/output (I/O) controllers 130which support connection by, and processing of signals from, one or moreconnected input device(s) 132, such as a keyboard, mouse, touch screen,or microphone. I/O controllers 130 also support connection to andforwarding of output signals to one or more connected output devices134, such as a monitor or display device or audio speaker(s).

Additionally, in one or more embodiments, IHS 100 includes a boardmanagement controller (BMC) 150, one or more cooling devices (CD) 152and one or more sensors 154. BMC 150 is in communication withprocessor(s) 105 and system memory 110 via system interconnect 115. BMC150 contains components that control specific operations of IHS 100 suchas power and thermal management. BMC 150 is in communication with CDs152 and sensors 154. CDs 152 can be one or more air movers, such asfans, that are positioned to cool IHS 100 during operation of IHS 100.Sensors 154 can include various types of sensors such as temperaturesensors, pressure sensors and flow sensors. Sensors 154 provide anelectrical signal to BMC 150 that is indicative of or proportional tothe quantity being read, measured or sensed by the sensor.

IHS 100 further includes power supply units (PSUs) 1-4 160A-D. PSUs160A-D provide a regulated source of power to IHS 100. PSUs 160A-D arecommunicatively coupled to BMC 150 by a communication bus 162. PSUs160A-D supply power to each of the components within IHS 100 thatrequire power via either one or more bus bars or power cables. BMC 150can receive power supply data, parameters and settings from PSUs 160A-Dvia communication bus 162. In one embodiment, several CDs 152, sensors154 and PSUs 160A-D can be mounted in IHS 100. The PSUs 160A-D arecontrolled via BMC 150 such that BMC 150 provides redundant powersupplies to IHS 100.

IHS 100 further comprises a network interface device (NID) 180. NID 180enables IHS 100 to communicate and/or interface with other devices,services, and components that are located external to IHS 100. Thesedevices, services, and components can interface with IHS 100 via anexternal network, such as example network 190, using one or morecommunication protocols. Network 190 can be a local area network, widearea network, personal area network, and the like, and the connection toand/or between network and IHS 100 can be wired or wireless or acombination thereof. For purposes of discussion, network 190 isindicated as a single collective component for simplicity. However, itis appreciated that network 190 can comprise one or more directconnections to other devices as well as a more complex set ofinterconnections as can exist within a wide area network, such as theInternet.

With reference now to FIG. 2A, there is illustrated one embodiment of aphysical layout 200 of components and zones within IHS 100. IHS 100includes a rack chassis or housing 205 that contains the components ofIHS 100. In one embodiment, housing 205 can contain a single IHS. Inanother embodiment, housing 205 can be representative of a server rackthat holds several IHSs. Housing 205 can have an interior cavity 207that can be divided into several compartments 210 and an open space 230.The temperature within housing 205 and compartments 210 can varydepending upon the location of the components, the airflow provided bythe CDs, and the amount of power being drawn by components of IHS 100.

Four hard disk drives (HDD) 225 are located at the top of housing 205.Memory cards 1-8 110A-H are mounted below open space 230 and (HDD) 225.Processors 1-4 105A-D are mounted in housing 205 below memory cards 1-8110A-H. CDs 1-6 152A-F are mounted in housing 205 below processors 1-4105A-D. One or more peripheral component interface (PCI) devices 220 andPSUs 1-4 160A-D are mounted at the bottom of housing 205. PSUs 1-2160A-B are mounted on a right side of housing 205 and PSUs 3-4 160C-Dare mounted on the left side of housing 205. Because of the open space230 and fewer HDDs 225 in the airflow path, the left side zone 1 240 ofinterior cavity 207 will have a lower airflow impedance (higher airflowrate) than the right side zone 2 245 of interior cavity 207. Forexample, in one empirical measurement study of physical layout 200, PSUs1-2 160A-B each had a steady state operating temperature of 40 degreesCentigrade and PSUs 3-4 160C-D each had a steady state operatingtemperature of 37 degrees Centigrade.

FIG. 2B illustrates another embodiment of a physical layout 250 ofcomponents and zones within IHS 100. IHS 100 includes a rack chassis orhousing 205 that contains the components of IHS 100. In one embodiment,housing 205 can contain a single IHS. In another embodiment, housing 205can be representative of a server rack that holds several IHSs. Housing205 can have an interior cavity 207 that can be divided into severalcompartments 210. The temperature within housing 205 and compartments210 can vary depending upon the location of the components, the airflowof the CDs, and the amount of power being drawn by components of IHS100.

Twenty-four hard disk drives (HDD) 255 are located at the top of housing205. Memory cards 1-4 110A-D and empty slots (ES) 260A-D are locatedbelow HDDs 255. Memory cards 1-4 110A-D are located on the right side ofhousing 205. Processors 1-2 105A-B are mounted in the right side ofhousing 205 below memory cards 1-4 110A-D. ES 260 E and F are locatedbelow ES 260A-D. CDs 1-6 152A-F are mounted in housing 205 belowprocessors 1-2 105A-B and below ES 260 E and F. One or more PCI devices220 and PSUs 1-4 160A-D are mounted at the bottom of housing 205. PSUs1-2 160A-B are mounted on a right side of housing 205 and PSUs 3-4160C-D are mounted on the left side of housing 205. Because of ES 260A-Fin the airflow path, the left side zone 1 280 of interior cavity 207will have a lower airflow impedance (higher airflow rate) than the rightside zone 2 285 of interior cavity 207. For example, in one empiricalmeasurement study of physical layout 250, PSUs 1-2 160A-B each had asteady state operating temperature of 40 degrees Centigrade and PSUs 3-4160C-D each had a steady state operating temperature of 32 degreesCentigrade.

PSUs 1-4 160A-D are geographically separated within housing 205. Becauseof the separation of the PSU, each PSU can experience differentoperating conditions and temperatures. The airflow path to the PSUs ischangeable due to the configuration of IHS 100, and specifically thecomponents that are in the airflow path. The heat generated by thecomponents is variable due to the changing workload of the systemcomponents.

FIG. 3 illustrates additional details of the PSUs and specifically PSU 1160A. PSU 1 160A comprises a housing 305, a PSU cooling device 310,temperature sensors (TS) 320, 322, micro-controller 330 and converter340. Converter 340 is communicatively coupled to micro-controller 330.Converter 340 can supply a controlled voltage and current to IHS 100.Converter 340 includes an input power meter (INPM) 360, an output powermeter (OUTPM) 362, one or more critical components (CC) 350 and acritical component temperature sensor (TS3) 324. INPM 360 can measurethe amount of input power drawn or used by PSU 1 160A. OUTPM 362 canmeasure the amount of output power produced by PSU 1 160A. CC 350 is oneor more components within PSU 1 160A. For example in one embodiment, CC350 can be the output switches or field effect transistors of theconverter.

TS3 324 is a temperature sensor that is located in proximity to CC 350and can monitor the temperature of CC 350. TS3 324 produces a voltagethat is proportional to the temperature sensed by the temperaturesensor. TS3 324 can be one of various types of temperature sensors suchas a thermistor, a thermocouple, a resistance thermometer or a siliconbandgap temperature sensor.

PSU 1 160A further includes a PSU cooling device 310, such as a fanmounted toward an air inlet side of PSU 1 160A. PSU cooling device 310is coupled to micro-controller 330 such that micro-controller 330 cancontrol the fan speed of PSU cooling device 310. PSU 1 160A alsoincludes an inlet air TS, TS1 320, and an exhaust air TS, TS2 322. TS1320 can sense the air temperature of air coming into PSU 1 160A and TS2322 can sense the air temperature of air being exhausted from PSU 1160A.

Each of PSU cooling device 310, temperature sensors (TS) 320, 322, and324 and converter 340 communicates with BMC 150 via micro-controller 330and communication bus 162. Micro-controller 330 is communicativelycoupled to BMC 150 via communication bus 162. BMC 150 contains one ormore input/output controllers that support connection to and processingof signals from micro-controller 330. BMC 150 can receive power supplydata, parameters and settings from micro-controller 330 viacommunication bus 162. BMC 150 utilizes the data and parameters receivedfrom micro-controller 330 to control PSU 1 160A.

BMC 150 can include a PSU control system 370 that controls the operationof PSUs 1-4 160A-D. PSU control system 370 includes BMC memory 372. Inone embodiment, BMC memory 372 can be a non-volatile or flash memorydevice. BMC memory 372 stores PSU control firmware 374. By executing PSUcontrol firmware 374, BMC 150 can determine configurations of PSUs160A-D such that certain PSUs are in an active mode and others in asleep mode, based on the thermal operating efficiency of the PSUs.

Those of ordinary skill in the art will appreciate that the hardwarecomponents and basic configurations depicted in FIGS. 1-3 and describedherein may vary. For example, the illustrative components within IHS 100(FIG. 1), housing 205 (FIG. 2) and PSU 1 160A (FIG. 3) are not intendedto be exhaustive, but rather are representative to highlight componentsthat can be utilized to implement aspects of the present disclosure. Forexample, other devices/components may be used in addition to or in placeof the hardware depicted. The depicted example does not convey or implyany architectural or other limitations with respect to the presentlydescribed embodiments and/or the general disclosure.

With reference now to FIG. 4A, one embodiment of example contents of BMCmemory 372 are shown. In the description of FIG. 4A, reference is alsomade to specific components illustrated within the preceding FIGS. 1-3.BMC memory 372 stores PSU control firmware 374. PSU control firmware 374controls which of the PSUs 160A-D are in an active mode and which of thePSUs 160A-D are in a sleep mode in IHS 100.

BMC memory 372 stores assigned weights 402 and mean time betweenfailures (MTBF) 404. Assigned weights 402 are pre-determined percentagevalues used in several calculated values for the PSUs. MTBFs 404 are thepredicted elapsed time between inherent failures for each of the PSUs inIHS 100. BMC memory 372 also stores PSU 1 parameters 410, PSU 2parameters 430, PSU 3 parameters 450 and PSU 4 parameters 470. PSU 1parameters 410 include input power 412 for various PSU loads as measuredby INPM 360, output power 414 for various PSU loads measured by OUTPM362, inlet air temperature 416 for various PSU loads measured by TS1320, exhaust air temperature 418 for various PSU loads measured by TS2322, and critical component temperature 420 for various PSU loadsmeasured by TS3 324. PSU 1 parameters 410 further include cooling devicefan speeds for various PSU loads 422, power dissipation 424 for variousPSU loads and PSU 1 thermal efficiency score (PTES) 426 for various PSUloads. Power dissipation 424 is the amount of power that is consumedinternally by PSU1 160A. PTES 426 is a calculated value that iscalculated from PSU 1 parameters 410.

For example, input power 412, output power 414, inlet air temperature416, exhaust air temperature 418, critical component temperature 420,and cooling device fan speeds 422 for various PSU loads can be measured,recorded and stored to BMC memory 372. In one embodiment, the PSU 1parameters 410 can be measured at total PSU loads of 100%, 90%, 80%,70%, 60%, 50%, 40%, 30%, 20% and 10%.

PSU 2 parameters 430 include input power 432, output power 434, inletair temperature 436, exhaust air temperature 438 and critical componenttemperature 440, cooling device fan speed 442, power dissipation 444 andPTES 446. PSU 3 parameters 450 include input power 452, output power454, inlet air temperature 456, exhaust air temperature 458 and criticalcomponent temperature 460, cooling device fan speed 462, powerdissipation 464 and PTES 466. PSU 4 parameters 470 include input power472, output power 474, inlet air temperature 476, exhaust airtemperature 478 and critical component temperature 480, cooling devicefan speed 482, power dissipation 484 and PTES 486.

As further illustrated, BMC memory 372 further stores total system powerload 487, inlet air temperature threshold 488, critical componenttemperature threshold 489, cooling device fan speed threshold 490, powercap 491, PSU configuration 492 and history table 494. Total system powerload 487 is the current amount of power required to operate processingcomponents and other functional components of IHS 100. Inlet airtemperature threshold 488, critical component temperature threshold 489,and cooling device fan speed threshold 490 are used to calculate thePTES scores. Power cap 491 is the total PSU output power load, and PSUconfiguration 492 is a list of the configuration of PSUs 160A-D requiredby IHS 100. For example, PSU configuration 492 can designate that atleast one of PSUs 160A-D are to be a hot spare PSU. History table 494can contain PSU parameters 410, 430, 450 and 470 that are received byBMC 150 and then stored to BMC memory 372.

Turning to FIGS. 4B and 4C, an example history table 494 for PSU 1 160Aand PSU 4 160D is shown. History table 494 is shown containing a portionof power supply parameters 410 and 470 for combinations of PSU 1 160Aand PSU 4 160D at various system power loads 495 that are percentages ofthe power cap. The combinations of PSU 1 160A and PSU 4 160D include PSU1 and 4 both active 496, PSU 1 active and PSU 4 in sleep mode 497 andPSU 1 in sleep mode and PSU 4 active 498.

The cells in history table 494 can contain, for PSU 1, the input power412, output power 414, and exhaust air temperature 418. The cells inhistory table 494 can contain, for PSU 4, the input power 472, outputpower 474, and exhaust air temperature 478. For example, at a systempower load of 100% and both PSU 1 and PSU 4 active, the PSU 1 inputpower 412 can be 196 watts, the output power 414 can be 182 watts, andthe exhaust air temperature 418 can be 53 degrees C. The PSU 4 inputpower 472 can be 190 watts, output power 474 can be 177 watts, and theexhaust air temperature 478 can be 52 degrees C. As shown in FIG. 4B, ata system load of 100%, the most power efficient combination of PSUs isfor both PSU 1 and PSU 4 to be active with a total input powerconsumption of 386 watts. The most power efficient combinations of thePSUs at each percentage system load is shown with cross-hatching inFIGS. 4B and 4C. In an embodiment, history table 494 can be generated byBMC 150 during start-up operations of IHS 100. In one embodiment,history table 494 can be generated by BMC 150 during a power on selftest (POST) performed by IHS 100.

FIGS. 5, 6A-6B and 7A-7B illustrate flowcharts of exemplary methods bywhich PSU control system 370 and BMC 150 within the preceding figuresperforms different aspects of the processes that enable the one or moreembodiments of the disclosure. Generally, method 500 represents acomputer-implemented method to determine active and sleep mode PSUsbased on PTES scores. Method 600 represents a computer-implementedmethod to determine active and sleep mode PSUs on a one time basisduring start-up of IHS 100. Method 700 represents a computer-implementedmethod to determine active and sleep mode PSUs on a real time basis.

The description of each method is provided with general reference to thespecific components illustrated within the preceding FIGS. 1-4C.Generally, each method is described as being implemented via theexecution of code provided by PSU control firmware 374 acting within BMC150 of IHS 100. It is however appreciated that certain aspects of thedescribed methods may be implemented via other processing devices and/orexecution of other code.

With specific reference to FIG. 5, method 500 begins at the start blockand proceeds to block 502 where BMC 150 determines the total systempower load 487 for IHS 100. At block 504, BMC 150 configures each of thePSUs 160A-D to equally share the total system power load 487. BMC 150triggers each of the PSUs 160A-D to transmit their respective PSUparameters 410, 430, 450 and 470 (block 506) and BMC 150 receives thePSU parameters 410, 430, 450 and 470 (block 508).

At block 510, BMC 150 calculates several PSU statistics for each of PSUs160A-D according to equations (1)-(5).

PSU inlet temperature margin=PSU inlet temperature specification488−actual PSU inlet air temperature (i.e. inlet air temperature 416 forPSU 1).  (1)

PSU critical component temperature margin=PSU critical componenttemperature specification 489−actual critical component temperature(i.e. CC temperature 420 for PSU 1).  (2)

PSU airflow=1.76×(PSU power dissipation (i.e. power diss. 424 for PSU1)/[PSU exhaust temperature (i.e. exhaust temp. 418 for PSU 1))−PSUinlet temperature (i.e. inlet temp. 416 for PSU 1)]. The constant 1.76applies when airflow is measured or provided in cubic feet per minute,power is measured or provided in watts and temperature is measured orprovided in degrees Celsius.  (3)

Percent maximum fan speed=cooling device fan speed (i.e. CD fan speed422 for PSU 1)/maximum cooling device fan speed 490×100.  (4)

Airflow efficiency quotient=PSU airflow/percent maximum fan speed.  (5)

At block 512, BMC 150 assigns a weight to each of the statisticscalculated in equations (1)-(5) based on pre-determined assigned weights402 stored in BMC memory 372. The assigned weights 402 arepre-determined by a user based on the relative importance of eachstatistic. For example the PSU inlet temperature margin can be assigneda weight of 50% and the PSU critical component temperature margin can beassigned a weight of 20%.

BMC 150 calculates the PTES values 426, 446, 466 and 486 according toequation (6) at block 514.

PTES=(PSU inlet temp. margin)×(0.5)+(PSU critical component temp.margin)×(0.2)+(Airflow efficiency quotient)×(0.3).  (6)

BMC 150 determines which PSUs have the highest PTES values and assignsthe PSUs with the highest PSUs scores that have sufficient capacity tohandle the total system power load 487 to be active PSUs in an activemode, and BMC 150 assigns the remaining PSUs to be in a sleep mode(block 516). BMC 150 configures the respective active PSUs to be in anactive mode and configures the respective sleep PSUs to be in a sleepmode (block 518). Method 500 then ends.

FIGS. 6A-6B illustrate details of method 600, which pre-populateshistory table 494 during the POST operation of IHS 100 to minimize there-characterization of the history table at run time. For simplicity indescribing the innovative features, method 600 is presented as beingimplemented within an example IHS (which is referred to as IHS 100′)having only two PSUs, PSUs 160A and 160D, which operate under differenttemperatures. However, it is appreciated that method 600 would beimplemented within IHS 100, using all four PSUs, i.e., PSUs 160A-D.Method 600 is applicable to all embodiments in which there are more thantwo PSUs, and can be applied to an IHS having a much larger number ofPSUs. Method 600 begins at the start block and proceeds to block 602where BMC 150 detects if IHS 100′ has powered on and entered POST. Atdecision block 604, BMC 150 determines if IHS 100′ has entered POST. Inresponse to IHS 100′ not entering POST, BMC 150 continues to detect ifIHS 100′ has powered on and entered POST at block 602. In response toIHS 100′ entering POST, BMC 150 triggers IHS 100′ to start a normalsystem workload which corresponds to production of a specific amount ofpower by PSUs 160A and D to support the operation of processingcomponents and other functional components within IHS 100′ (block 606).BMC 150 triggers PSUs 160A and D to transmit each of their output powerloads or levels 414 and 474, respectively, to BMC 150 (block 608). BMC150 receives the output power loads or levels 414 and 474 (block 610)and sets power cap 491 equal to the sum of the total output power loads414 and 474 (block 614).

At decision block 616, BMC 150 determines if the power cap 491 is equalto 0% of the total output power load. In response to the power cap 491not being equal to 0% of the total output power load, BMC 150 configuresboth of PSUs 160A and D to be active and in an “on” state supplyingpower to IHS 100′ (block 618). BMC 150 determines if the PSUs 160A and Dhave reached a thermal steady state (decision block 620). In response tothe PSUs 160A and D not being in thermal steady state, BMC 150 continuesto determine if the PSUs 160A and D have reached a thermal steady stateat decision block 620. In response to the PSUs 160A and D being in athermal steady state, BMC 150 triggers PSUs 160A and D to measure andtransmit to BMC 150 each of the PSU's respective input power 412 and472, output power 414 and 474, and temperatures from TS 1, 2, and 3 416,418, 420 and 476, 478 and 480 (block 622).

BMC 150 reduces the power cap by 10% (block 624) and returns to decisionblock 616 to continue checking if the power cap 491 is equal to 0% ofthe total output power load. In response to the power cap 491 not beingequal to 0% of the total output power load, BMC 150 repeats blocks 618to 624 until the power cap 491 is equal to 0% of the total output powerload. In response to the power cap 491 being equal to 0% of the totaloutput power load, BMC 150 sets power cap 491 equal to the sum of thetotal output power loads 414 and 474 (block 626). At decision block 628,BMC 150 determines if the power cap 491 is equal to 0% of the totaloutput power load. In response to the power cap 491 not being equal to0% of the total output power load, BMC 150 configures PSU 160A to beactive and in an “on” state or mode and configures PSU 2 160D to be in asleep mode (block 630). BMC 150 determines if the PSUs 160A and D havereached a thermal steady state (decision block 632). In response to thePSUs 160A and D not being in thermal steady state, BMC 150 continues todetermine if the PSUs 160A and D have reached a thermal steady state atdecision block 632.

In response to the PSUs 160A and D being in a thermal steady state, BMC150 triggers PSUs 160A and D to measure and transmit each of theirrespective input power 412 and 472, output power 414 and 474, andtemperatures 416, 418, 420 and 476, 478 and 480 to BMC 150 (block 634).BMC 150 reduces the power cap by 10% (block 636) and returns to decisionblock 628 to continue checking if the power cap 491 is equal to 0% ofthe total output power load. In response to the power cap 491 not beingequal to 0% of the total output power load, BMC 150 repeats blocks 630to 636 until the power cap 491 is equal to 0% of the total output powerload.

In response to the power cap 491 being equal to 0% of the total outputpower load, BMC 150 sets power cap 491 equal to the sum of the totaloutput power loads 414 and 474 (block 638). At decision block 640, BMC150 determines if the power cap 491 is equal to 0% of the total outputpower load. In response to the power cap 491 not being equal to 0% ofthe total output power load, BMC 150 triggers PSU 160D to be active andin an on state or mode and PSU 160A to be in a sleep mode (block 642).BMC 150 determines if the PSUs 160A and D have reached a thermal steadystate (decision block 644). In response to the PSUs 160A and D not beingin thermal steady state, BMC 150 continues to determine if the PSUs 160Aand D have reached a thermal steady state at decision block 644.

In response to the PSUs 160A and D being in a thermal steady state, BMC150 triggers PSUs 160A and D to measure and transmit each of theirrespective input power 412 and 472, output power 414 and 474, andtemperatures 416, 418, 420, and 476, 478 and 480 to BMC 150 (block 646).BMC 150 reduces the power cap by 10% (block 648) and returns to decisionblock 640 to continue checking if the power cap 491 is equal to 0% ofthe total output power load. In response to the power cap 491 not beingequal to 0% of the total output power load, BMC 150 repeats blocks 642to 648 until the power cap 491 is equal to 0% of the total output powerload.

In response to the power cap 491 being equal to 0% of the total outputpower load, BMC 150 generates history table 494 based on the receivedinput powers, output powers, and temperatures for each power cap level491 (block 649). BMC 150 stores the history table 494 to BMC memory 372(block 650). BMC 150 stops the system workload (block 652) and allowsthe POST to finish operation (block 654). Method 600 then ends.

Method 600 generates history table 494 for different load and powervalues for various combination of active and sleep mode PSUs. Method 600characterizes the operation of the PSUs for a range of operatingconditions on a one-time basis during POST. History table 494 can thenbe referenced at runtime by IHS 100. The PSU configuration correspondingto the operating conditions that provide optimal performance can beselected for use as will be explained in further detail in FIG. 7.

FIG. 7A-B illustrates details of method 700 to determine active andsleep mode PSUs on a real time basis within IHS 100. Method 700 isimplemented within IHS 100 using PSUs 1 160A and 4 160D. However, method700 can be implemented with more than two PSUs and up to hundreds ofPSUs in an IHS. Method 700 begins at the start block and proceeds toblock 702 where BMC 150 retrieves history table 494 from BMC memory 372.

At decision block 704, BMC 150 determines if history table 494 containsdata for the current percentage of the power cap 491 (i.e. load) thatthe PSUs in IHS 100 (i.e. PSU 1 160A and PSU 4 160D) are currentlyoperating at. In response to history table 494 not containing data forthe current percentage of the power cap 491 that the PSUs are operatingat, BMC 150 extrapolates a predictive configuration of PSUs that are inan active mode and PSUs that are in a sleep mode (block 706). In oneembodiment, the extrapolation utilizes the table data for the twopercentages that are above and below the detected current percentage ofpower cap. BMC 150 determines if the predicted PSU configuration is forboth PSU 1 160A and PSU 4 160D to be active (decision block 708). Inresponse to the predicted PSU configuration being that both PSU 1 160Aand PSU 4 160D are to be active, BMC 150 triggers both of PSU 1 160A andPSU 4 160D to be active and operational (block 710). BMC 150 alsodetermines if PSU 1 160A and PSU 4 160D have reached a thermal steadystate (decision block 712). In response to PSU 1 160A and PSU 4 160D notbeing in thermal steady state, BMC 150 continues to determine if PSU 1160A and PSU 4 160D have reached a thermal steady state at decisionblock 712. In response to PSU 1 160A and PSU 4 160D being in a thermalsteady state, BMC 150 triggers PSU 1 160A and PSU 4 160D to measure andtransmit each of their respective input power 412 and 472, output power414 and 474, and temperatures 416, 418, 420, and 476, 478, 480 to BMC150 (block 714).

After block 714 and in response to the predicted PSU configuration notbeing for both PSU 1 160A and PSU 4 160D to be active, BMC 150determines if the predicted PSU configuration is for PSU 1 160A to beactive and PSU 4 160D to be in a sleep mode (decision block 716). Inresponse to the predicted PSU configuration being for PSU 1 160A to beactive and PSU 4 160D to be in a sleep mode, BMC 150 triggers PSU 1 160Ato be active and PSU 4 160D to be in a sleep mode (block 718), and BMC150 determines if PSU 1 160A and PSU 4 160D have reached a thermalsteady state (decision block 720). In response to PSU 1 160A and PSU 4160D not being in thermal steady state, BMC 150 continues to determineif PSU 1 160A and PSU 4 160D have reached a thermal steady state atdecision block 720. In response to PSU 1 160A and PSU 4 160D being in athermal steady state, BMC 150 triggers PSU 1 160A and PSU 4 160D tomeasure and transmit each of their respective input power 412 and 472,output power 414 and 474, and temperatures 416, 418, 420, and 476, 478,480 to BMC 150 (block 722).

After block 722 and in response to the predicted PSU configuration notbeing for PSU 1 160A to be active and PSU 4 160D to be in a sleep modeactive, BMC 150 determines if the predicted PSU configuration is for PSU1 160A to be in a sleep mode and PSU 4 160D to be in an active mode(decision block 724). In response to the predicted PSU configurationbeing for PSUs 1 160A to be in a sleep mode and PSU 4 160D to be active,BMC 150 triggers PSU 1 160A to be in a sleep mode and PSU 4 160D to beactive (block 726), and BMC 150 determines if PSU 1 160A and PSU 4 160Dhave reached a thermal steady state (decision block 728). In response toPSU 1 160A and PSU 4 160D not being in thermal steady state, BMC 150continues to determine if PSU 1 160A and PSU 4 160D have reached athermal steady state at decision block 728. In response to PSU 1 160Aand PSU 4 160D being in a thermal steady state, BMC 150 triggers PSU 1160A and PSU 4 160D to measure and transmit each of their respectiveinput power 412 and 472, output power 414 and 474, and temperatures 416,418, 420, and 476, 478, 480 to BMC 150 (block 730).

BMC 150 stores the received input power 412 and 472, output power 414and 474, and temperatures 416, 418, 420, and 476, 478, 480 to BMC memory372 (block 732). After block 732 and in response to the predicted PSUconfiguration being for PSUs 1 160A to be in a sleep mode and PSU 4 160Dto be active, BMC 150 determines if the lowest power configuration ofPSUs 1 160A and PSU 4 160D is the preferred combination of PSUs(decision block 734). In one embodiment, the lowest power configurationis the combination of PSUs with the lowest combined input power 412 and472 at a corresponding percentage load.

In response to the lowest power configuration of PSUs 1 160A and PSU 4160D being preferred, BMC 150 selects the configuration of PSUs havingthe lowest power (block 736). In response to the lowest powerconfiguration of PSUs 1 160A and PSU 4 160D not being preferred, BMC 150selects the configuration of PSUs having the highest mean time betweenfailure (MTBF) from MTBF list 404 (block 738). After blocks 736 and 738,BMC 150 selects at least one of the non-active PSUs (i.e. one of thesleep mode PSUs) to be hot and cold spare PSUs (block 740).

BMC 150 triggers the lowest power configuration of the PSUs to be in anactive or sleep mode at their respective percentage loads (block 741).The lowest power configuration is the combination of PSUs with thelowest combined input power 412 and 472 at a corresponding percentageload. At block 742, BMC 150 monitors the PSU operating parameters bytriggering the PSUs to measure and transmit each of their respectiveinput powers, output powers, and temperatures during operation. BMC 150determines if there has been a change in the values of the respectiveinput powers, output powers, and temperatures for the PSUs (decisionblock 744). In response to determining there has not been a change inthe values of the respective input powers, output powers, andtemperatures for the PSUs, BMC 150 continues monitoring the PSUoperating parameters at block 742. In response to determining there hasbeen a change in the values of the respective input powers, outputpowers, and temperatures for the PSUs, BMC 150 returns to block 704where BMC 150 again continues to determine if history table 494 containsdata for the current percentage of the power cap 491 (i.e. percentageload) that the PSUs in IHS 100 are currently operating at.

In the above described flow chart, one or more of the methods may beembodied in a computer readable medium containing computer readable codesuch that a series of functional processes are performed when thecomputer readable code is executed on a computing device. In someimplementations, certain steps of the methods are combined, performedsimultaneously or in a different order, or perhaps omitted, withoutdeviating from the scope of the disclosure. Thus, while the methodblocks are described and illustrated in a particular sequence, use of aspecific sequence of functional processes represented by the blocks isnot meant to imply any limitations on the disclosure. Changes may bemade with regards to the sequence of processes without departing fromthe scope of the present disclosure. Use of a particular sequence istherefore, not to be taken in a limiting sense, and the scope of thepresent disclosure is defined only by the appended claims.

Aspects of the present disclosure are described above with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems) and computer program products according to embodiments of thedisclosure. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer program instructions. Computer program code for carrying outoperations for aspects of the present disclosure may be written in anycombination of one or more programming languages, including an objectoriented programming language, without limitation. These computerprogram instructions may be provided to a processor of a general purposecomputer, special purpose computer, such as a service processor, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, performs the method forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks.

One or more of the embodiments of the disclosure described can beimplementable, at least in part, using a software-controlledprogrammable processing device, such as a microprocessor, digital signalprocessor or other processing device, data processing apparatus orsystem. Thus, it is appreciated that a computer program for configuringa programmable device, apparatus or system to implement the foregoingdescribed methods is envisaged as an aspect of the present disclosure.The computer program may be embodied as source code or undergocompilation for implementation on a processing device, apparatus, orsystem. Suitably, the computer program is stored on a carrier device inmachine or device readable form, for example in solid-state memory,magnetic memory such as disk or tape, optically or magneto-opticallyreadable memory such as compact disk or digital versatile disk, flashmemory, etc. The processing device, apparatus or system utilizes theprogram or a part thereof to configure the processing device, apparatus,or system for operation.

As will be further appreciated, the processes in embodiments of thepresent disclosure may be implemented using any combination of software,firmware or hardware. Accordingly, aspects of the present disclosure maytake the form of an entirely hardware embodiment or an embodimentcombining software (including firmware, resident software, micro-code,etc.) and hardware aspects that may all generally be referred to hereinas a “circuit,” “module,” or “system.” Furthermore, aspects of thepresent disclosure may take the form of a computer program productembodied in one or more computer readable storage device(s) havingcomputer readable program code embodied thereon. Any combination of oneor more computer readable storage device(s) may be utilized. Thecomputer readable storage device may be, for example, but not limitedto, an electronic, magnetic, optical, electromagnetic, infrared, orsemiconductor system, apparatus, or device, or any suitable combinationof the foregoing. More specific examples (a non-exhaustive list) of thecomputer readable storage device would include the following: anelectrical connection having one or more wires, a portable computerdiskette, a hard disk, a random access memory (RAM), a read-only memory(ROM), an erasable programmable read-only memory (EPROM or Flashmemory), an optical fiber, a portable compact disc read-only memory(CD-ROM), an optical storage device, a magnetic storage device, or anysuitable combination of the foregoing. In the context of this document,a computer readable storage device may be any tangible medium that cancontain, or store a program for use by or in connection with aninstruction execution system, apparatus, or device.

While the disclosure has been described with reference to exemplaryembodiments, it will be understood by those skilled in the art thatvarious changes may be made and equivalents may be substituted forelements thereof without departing from the scope of the disclosure. Inaddition, many modifications may be made to adapt a particular system,device or component thereof to the teachings of the disclosure withoutdeparting from the essential scope thereof. Therefore, it is intendedthat the disclosure not be limited to the particular embodimentsdisclosed for carrying out this disclosure, but that the disclosure willinclude all embodiments falling within the scope of the appended claims.Moreover, the use of the terms first, second, etc. do not denote anyorder or importance, but rather the terms first, second, etc. are usedto distinguish one element from another.

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to be limiting of the disclosure.As used herein, the singular forms “a”, “an” and “the” are intended toinclude the plural forms as well, unless the context clearly indicatesotherwise. It will be further understood that the terms “comprises”and/or “comprising,” when used in this specification, specify thepresence of stated features, integers, steps, operations, elements,and/or components, but do not preclude the presence or addition of oneor more other features, integers, steps, operations, elements,components, and/or groups thereof.

The description of the present disclosure has been presented forpurposes of illustration and description, but is not intended to beexhaustive or limited to the disclosure in the form disclosed. Manymodifications and variations will be apparent to those of ordinary skillin the art without departing from the scope of the disclosure. Thedescribed embodiments were chosen and described in order to best explainthe principles of the disclosure and the practical application, and toenable others of ordinary skill in the art to understand the disclosurefor various embodiments with various modifications as are suited to theparticular use contemplated.

1. A computer implemented method for determining a power supply unit(PSU) configuration in an information handling system (IHS), the methodcomprising: determining, via a controller, a first amount of powerrequired to operate functional components of the IHS, the first amountof power correlating to a present percentage load on a plurality of PSUsutilized to power the IHS; retrieving a history table containing aplurality of PSU configurations and PSU data, the PSU configurationscomprising combinations of active mode and sleep mode PSUs for each of aplurality of percentage loads; determining if the history table containsa first PSU configuration corresponding to the first amount of powerrequired to operate the functional components of the IHS; and inresponse to determining that the history table contains the first PSUconfiguration, configuring the PSUs identified as active mode PSUs inthe first PSU configuration to be in an active mode and collectivelyoperating at the corresponding percentage load and configuring the PSUsidentified as sleep mode PSUs in the first PSU configuration to be in asleep mode.
 2. The method of claim 1, wherein in response to determiningthat the history table does not contain the first PSU configuration, themethod further comprises: extrapolating a predictive combination ofactive and sleep mode PSUs; and configuring the PSUs identified asactive mode PSUs in the predictive combination to be in an active modeand triggering the PSUs identified in the predictive combination assleep mode PSUs to be in a sleep mode.
 3. The method of claim 1, whereinin response to determining that the history table does not contain thefirst PSU configuration, the method further comprises: triggering eachof the plurality of PSUs to transmit respective PSU parametersassociated with operation of the PSUs for the plurality of percentageloads; determining a second PSU configuration having a lowest totalinput power that supports the present percentage load; and triggeringactivation of the second configuration of PSUs.
 4. The method of claim1, wherein the history table is generated during a power on self test(POST) of the IHS prior to initiating processing operations.
 5. Themethod of claim 4, wherein generating the history table furthercomprises: configuring the PSUs to be in a plurality of combinations ofactive and sleep modes; triggering each of the PSUs to transmit aplurality of PSU parameters associated with operation of the PSU at eachof the plurality of percentage loads and for each of the plurality ofcombinations; and storing, as the plurality of PSU configurations, thePSU parameters for the plurality of percentage loads for each of theplurality of combinations.
 6. The method of claim 1, further comprising:receiving a plurality of power supply parameters for each of the PSUs;calculating a power supply thermal efficiency score (PTES) based on thepower supply parameters; determining which of the PSUs have the highestPTES values; and identifying the PSUs with the highest PTES values andcapacity to support the first amount of power as the active mode PSUsand identifying the remaining PSUs as the sleep mode PSUs.
 7. The methodof claim 6, wherein calculating the PTES value further comprises:calculating a plurality of PSU statistics for each of the PSUs at leastpartially based on the power supply parameters; and assigning weights toeach of the PSU statistics, wherein the PTES values are calculated basedon the PSU statistics and the assigned weights.
 8. A power supply systemcomprising: a plurality of power supply units (PSUs) supplying power toan information handling system (IHS); a controller communicativelycoupled to the PSUs, the controller having firmware executing thereon todetermine a PSU configuration to apply to the IHS, wherein the firmwareconfigures the controller to: determine a first amount of power requiredto operate functional components of the IHS, the first amount of powercorrelating to a present percentage load on a plurality of PSUs utilizedto power the IHS; retrieve a history table containing a plurality of PSUconfigurations and PSU data, the PSU configurations comprisingcombinations of active mode and sleep mode PSUs for each of a pluralityof percentage loads; determine if the history table contains a first PSUconfiguration corresponding to the first amount of power required tooperate the functional components of the IHS; and in response todetermining that the history table contains the first PSU configuration,configure the PSUs identified as active mode PSUs in the first PSUconfiguration to be in an active mode and collectively operating at thecorresponding percentage load and configure trigger the PSUs identifiedas sleep mode PSUs in the first PSU configuration to be in a sleep mode.9. The power supply system of claim 8, wherein in response todetermining that the history table does not contain the first PSUconfiguration corresponding to the first amount of power required tooperate functional components of the IHS, the controller: extrapolates apredictive combination of active and sleep mode PSUs; and configures thePSUs identified as active mode PSUs in the predictive combination to bein an active mode and configures the PSUs identified in the predictivecombination as sleep mode PSUs to be in a sleep mode.
 10. The powersupply system of claim 8, wherein in response to determining that thehistory table does not contain the first PSU configuration correspondingto the first amount of power required to operate functional componentsof the IHS, the controller: triggers each of the PSUs to transmit aplurality of PSU parameters associated with operation of the PSUs forthe plurality of percentage loads; determines a second PSU configurationhaving a lowest total input power that supports the present percentageload; and triggers activation of the second configuration of PSUs. 11.The power supply system of claim 8, wherein the history table isgenerated during a power on self test (POST) of the IHS prior tobeginning processing operations and wherein to generate the historytable the controller: configures the PSUs to be in a plurality ofcombinations of active and sleep modes; triggers each of the PSUs totransmit a plurality of PSU parameters associated with operation of thePSU at each of the plurality of percentage loads and for each of theplurality of combinations; and stores the PSU parameters for theplurality of percentage loads for each of the plurality of combinationsas the plurality of PSU configurations.
 12. The power supply system ofclaim 8, wherein the firmware further configures the controller to:receive a plurality of power supply parameters for each of the PSUs;calculate a power supply thermal efficiency score (PTES) based on thepower supply parameters; determine which of the PSUs have the highestPTES values; and identify the PSUs with the highest PTES values andcapacity to support the first amount of power as the active mode PSUsand identifying the remaining PSUs as the sleep mode PSUs.
 13. The powersupply system of claim 12, wherein to calculate the PTES value, thecontroller: calculates a plurality of PSU statistics for each of thePSUs at least partially based on the power supply parameters; andassigns weights to each of the PSU statistics, wherein the PTES valuesare calculated based on the PSU statistics and the assigned weights. 14.An information handling system (IHS) comprising: a processor; aplurality of power supply units (PSUs) supplying power to the IHS; acontroller communicatively coupled to the PSUs, the controller havingfirmware executing thereon to determine a PSU configuration to apply tothe IHS, wherein the firmware configures the controller to: determine afirst amount of power required to operate functional components of theIHS, the first amount of power correlating to a present percentage loadon a plurality of PSUs utilized to power the IHS; retrieve a historytable containing a plurality of PSU configurations and PSU data, the PSUconfigurations comprising combinations of active mode and sleep modePSUs for each of a plurality of percentage loads; determine if thehistory table contains a first PSU configuration corresponding to thefirst amount of power required to operate the functional components ofthe IHS; and in response to determining that the history table containsthe first PSU configuration, configure r the PSUs identified as activemode PSUs in the first PSU configuration to be in an active mode andcollectively operating at the corresponding percentage load andconfigure the PSUs identified as sleep mode PSUs in the first PSUconfiguration to be in a sleep mode.
 15. The information handling systemof claim 14, wherein in response to determining that the history tabledoes not contain the first PSU configuration corresponding to the firstamount of power required to operate functional components of the IHS,the controller: extrapolates a predictive combination of active andsleep mode PSUs; and triggers the PSUs identified as active mode PSUs inthe predictive combination to be in an active mode and triggers the PSUsidentified in the predictive combination as sleep mode PSUs to be in asleep mode.
 16. The information handling system of claim 14, wherein inresponse to determining that the history table does not contain thefirst PSU configuration corresponding to the first amount of powerrequired to operate functional components of the IHS, the controller:triggers each of the PSUs to transmit a plurality of PSU parametersassociated with operation of the PSUs for the plurality of percentageloads; determines a second PSU configuration having a lowest total inputpower that supports the present percentage load; and triggers activationof the second configuration of PSUs.
 17. The information handling systemof claim 14, wherein the history table is generated during a power onself test (POST) of the IHS prior to beginning processing operations.18. The information handling system of claim 17, wherein to generate thehistory table the controller: configures the PSUs to be in a pluralityof combinations of active and sleep modes; triggers each of the PSUs totransmit a plurality of PSU parameters associated with operation of thePSU at each of the plurality of percentage loads and for each of theplurality of combinations; and stores the PSU parameters for theplurality of percentage loads for each of the plurality of combinationsas the plurality of PSU configurations.
 19. The information handlingsystem of claim 14, wherein the firmware further configures thecontroller to: receive a plurality of power supply parameters for eachof the PSUs; calculate a power supply thermal efficiency score (PTES)based on the power supply parameters; determine which of the PSUs havethe highest PTES values; and identify the PSUs with the highest PTESvalues and capacity to support the first amount of power as the activemode PSUs and identifying the remaining PSUs as the sleep mode PSUs. 20.The power supply system of claim 19, wherein to calculate the PTESvalue, the controller: calculates a plurality of PSU statistics for eachof the PSUs at least partially based on the power supply parameters; andassigns weights to each of the PSU statistics, wherein the PTES valuesare calculated based on the PSU statistics and the assigned weights.